home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
rfw_v120.zip
/
RFWDOCEN.DOC
< prev
next >
Wrap
Text File
|
1993-02-08
|
82KB
|
1,535 lines
╔══════════════════════════════ ┌─────────────────┐
║ RFC/W Remote Access │ D.I.S.P. │────┐
║ Windowed file-list │ │░░░░│
╟────────────────────────────── │ │░░░░│
║ (c) 1993 Robert W.van Hoeven │ Dutch │░░░░│
╟────────────────────────────── │ Independent │░░░░│
║ Release : 1.20 │ ShareWare │░░░░│
║ Rel.Date: 8th February 1993 │ Programmer│░░░░│
╠══════════════════════════════ └─────────────────┘░░░░│
║ | │░░░░░░░░░░░░░░░░░│
║ │ RFC.EXE / RFCCFG.EXE | └─────────────────┘
║ │ RFW.EXE / RFWCFG.EXE | ┌─────┐ |
║ │ | │░░░░░│ |
║ │ | └──┬──┘ |
║ │ Lines starting with '│' are | ┌────┴────┐ |
║ │ changes from version 1.16 ! ------││││││ ═══│-------
║ └─────────┘
╠═══════════════════════════════
║ Address: Robert W. van Hoeven
║ PO. Box 131
║ 1170 AC Badhoevedorp
║ Nederland / Holland
╚═══════════════════════════════
┌───────┬─────────────────────────────────────────────────────────────┐
│ 0 │ Table of contents │
└───────┴─────────────────────────────────────────────────────────────┘
1 ---- General information
1.1 Copyrights and License Agreement
1.2 Newer versions and contacting the author
2 ---- Package description and requirements
2.1 Preface
2.2 Requirements
2.3 Included files
2.4 History
2.5 Multi-taskers
3 ---- Installation description
3.1 Installation
3.2 Install RFC
3.3 Install RFW
3.4 BBS menu options
4 ---- Runtime information
4.1 Calling RFW
4.2 FileDoor/DISP-compatible tag-file <tm>
5 ---- Version information and credits
5.1 The BETA-team
5.2 Credits
5.3 Version history
5.4 Copyright, Trademarks
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1 │ General information │
└───────┴─────────────────────────────────────────────────────────────┘
1.1 Copyrights and License Agreement
────────────────────────────────────
- Users of the RFW-package must accept this disclaimer of warranty:
- The RFW-package is supplied as is. The author disclaims all
warranties, expressed or implied, including, without limitation, the
warranties of merchantability and of fitness for any purpose. The
author assumes no liability for damages, direct or consequential,
which may result from the use of the RFW-package;
- The RFW-package is a "shareware program" and is provided at no
charge to the user for evaluation. Feel free to share it with your
friends, but please do not give it away altered or as part of
another system. The essence of "user-supported" software is to
provide personal computer users with quality software without high
prices, and yet to provide incentive for programmers to continue to
develop new products.
- If you find this program useful and find that you are using and
continue the use of the RFW-package after a 30 days trial period,
you must register the RFW-package as described below;
- Non-commercial can get a license for the usage up to this release of
the RFW-package for a small amount of money. Look into the details
in REGISTER.RFW. Previous registered users will receive a big
reduction to upgrade to the newer versions. These users should look
into the details in UPGRADE.RFW. For Non-commercial users there is
a POSSIBILITY to submit to one of the special contracts as explained
in the file REGISTER.RFW.
- Commercial usage of RFW will cost somewhat more. Also, a so called
'closed' Bulletin Board System (a system where the user must pay
direct to the SysOp to get full access) is has to pay more than a
Non-commercial user. Both types of users should look into the
details in REGISTER.RFW;
- The registration of the RFW-package will license ONE copy for use on
any computer at any one time, as long as the usage confirms to the
type of registration you have done (so NON-commercial usage when you
have a non-commercial license);
- Anyone distributing the RFW-package for any kind of remuneration
must first contact the Author at the address above for
authorization.
- You are encouraged to pass a copy of the RFW-package along to
your friends for evaluation. Please encourage them to register
their copy if they find that they can use it;
- Support on RFW, when used in a non-commercial environment, is
available by means of written letters or by entering the inter-
national echomail area DISP;
- Problems and suggestions can be entered in the FidoNet <tm> Echomail
conference <tm> called DISP (international). Entering this echo does
not exclude you of the duty to register the RFW-package, though
users who evaluate the product can enter the echo for questions;
- The RFW-package, all programs, the documentation and support-files
is copyrighted 1990,92 by Robert W. van Hoeven, PO. Box 131,
Badhoevedorp 1170AC, Holland. All rights are reserved. You may copy
this package for backup purposes. Also you may copy and share
unmodified copies of the whole package, providing that the copyright
notice is reproduced and included on all copies.
Excluded from this statement are the support-files written by other
authors. Please refer to the documentation of these programs for
copyrights and license agreements;
- It is forbidden to modify, adapt, translate, reverse engineer,
decompile and/or disassemble the software in the RFW-package.
Patching the medium at places that carry the software is seen as a
program change and is also forbidden. It is forbidden to create a so
called 'bypass' to skip the original introduction screens and delay.
Also it is forbidden to use such a 'bypass' unless supplied by the
author (Robert W. van Hoeven) himself;
- Performing any of the illegal actions as stated in the previous
lines, is a theft and no fair play to the author and, more
important, to the registered users;
- Bulletin Board Systems that distribute the RFW package can convert
the WHOLE package to any archive-system they like but all original
files must be included in the new archive. The RFW-package on the
Bulletin Board can contain at the most 2 extra files. These files
can only be a commercial for that Bulletin Board and/or validation
data that is presented as a service to all users and shall have no
other functions;
- After the normal trial period of 30 days, you must register the
soft- ware (see REGISTER.RFW) or you must remove it from your PC;
- Comments, suggestions and bug reports are welcome and will be
answered as soon I have the time to do so. You can send me a letter
of leave a NetMail <tm> message named to Rob Van.hoeven (mind the
point) on node 2:512/100 (RA Support, Monster, Holland, SysOp is
Reinier de Groot). When you want to send me normal mail, address it
to: Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp,
Holland; Also you can enter messages in the FidoNet <tm> DISP
Echomail <tm> area;
1.2 Newer versions and contacting the author
───────────────────────────────────────────────────────────────────────
The newest version of RFW is always available at the DISP-HQ on node
2:512/100. RFW is also distributed thru a number of DISP support
nodes. There are three ways of obtaining newer versions of RFW:
- Logging on at DISP-HQ or a support node
Look into the file SUPPORT.RFW for a full list of support nodes;
- Logging on to a SDS node
RFW is distributed thru SDS/SDN, but only big minors (x.10, x.20 and
so on) and majors (14.01, 15.01 and so on) are submitted to the SDS
distribution point in Holland;
- Logging on to your own BBS;
Chances are, that you will find an older version (international
users) because it will take some time for the new version to 'bleed'
thru the net;
- Update service;
You can enter a special update service (read REGISTER.RFW).
If you think you have found problems in RFW, or in any other case, you
wish to contact the author, you can send me:
- A letter to the address you can find in the header of this file;
- A NetMail <tm> message to Rob Van.hoeven (please mind the point
between Van and Hoeven) at 2:512/100 or (better) 2:512/100.5;
- A Message in the FidoNet <tm> DISP echomail <tm> area;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 2 │ Package description and requirements │
└───────┴─────────────────────────────────────────────────────────────┘
2.1 Preface
────────────────────────────────────────────────────────────────────────
This program, dating from the 1990's, was the followup of the first
try to create a windowed file-lister with tag capabilities. It was the
first program for RA/QBBS/SBBS alike BBS-programs that contained
windowed list functions and the option to tag files for later
reference from other programs ! Currently, the combination of RFW
<tm>, MTS <tm> and FileDoor <tm> can replace almost all your
file-access in your bulletin-board and these three programs can all
work with the tag-file (DISP/FileDoor compatible tag-file <tm>), which
can be created by RFW.
After RFW (and its older brother QFF) was released, a number of other
clones hit the market, but RFW has still a major share, though some
other listers tried (successfully) to gain on speed or possibilities.
In my opinion, it is not the speed but the added options in RFW that
still make it a nice program to use (and it is still free of charge
when used in a non-commercial environment).
Also a point to remember is, that most BBS systems now also support a
kind of tagging. Some of them do this in a compatible way, being able
to create a DISP/FileDoor compatible tag-file. In this case the user
still has the option to use one or more products from the BBS
internally, but replace one or more by doors. From the point of view
of the Sysop (and user) this is very thoughtful of the authors of the
BBS. To reverse the matter, those BBS programs that create an
interface of their own (with their own, non compatible, tag-files) are
less flexible. It comes to mind that these authors are trying to keep
out some of the good door products that have been created by many
people over the last years.
Currently I am working on RFW 2.01 which will contain a complete new
user-interface, making it almost look the same as a database browse
program. The 2.01 version of RWF will take some months though, because
a number of routines must be rewritten to make it both flexible AND
fast. In the meanwhile, this in-between release of RFW (with the old
interface) is released, to grant a number of much asked suggestions
and to fix a number of bugs (most of them were cosmetic bugs).
2.2 Requirements
────────────────────────────────────────────────────────────────────────
RFW requires: - PC XT/AT/386/486
- At least 160K free memory;
- DOS 3.xx and higher;
(tested with 4Dos 4.01, should work with lower
versions);
- HDU optional
- A Bulletin Board System. Directly supported are
the QuickBBS, SuperBBS and Remote Access types;
2.3 Included files
────────────────────────────────────────────────────────────────────────
The package includes : RFW.EXE The main lister program
RFWCFG.EXE Configuration program for RFW
RFC.EXE The main compiler program
RFWCFG.EXE Configuration program for RFC
RFWHLP.ANS Example help-file for ANSI users
RFWHLP.ASC Example help-file for ASCII users
2.4 History
────────────────────────────────────────────────────────────────────────
RFW came as an extended followup of the QFF program, which comes with
the 'Quick File Vacuumcleaner' <tm> package (called QFV). This QFV
package is very large and the QFF program is only a small part of the
package (which main objective is to automate file-management on a
BBS).
QFF will also be enhanced in a later stage. When both RFW and QFF are
enhanced (end '92), they will both use the same types of databases to
scroll thru the files in a VERY fast way and users can choose the type
of interface they like most (either RWF or QFF), though both programs
go from a different point of view (RFW is windowed, QFF is a page by
page viewer).
In the years, QFV/QFC/QFF on one side and FileDoor, MTS and RFW on the
other side have created a sort of standard for extra comment lines in
the FILES.BBS (starting with a '+' character). This release of RFW
maintains that standard. Also lines in FILES.BBS that are up to 255
bytes in length ARE observed by RFW. If one should come up with a
better idea, let me know. Most important products (like file-area
managers) can now handle these +-comment lines.
2.5 Multi-taskers
────────────────────────────────────────────────────────────────────────
RFW is aware of multi-taskers. When SHARE is loaded (and even when it
isn't), RFW will share the pre-compiled database with other (concur-
rent) RFW tasks. RFC (the compiler) will use the database on an
exclusive basis, so you need to run the compiler somewhere in an
event.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 3 │ Installation description │
└───────┴─────────────────────────────────────────────────────────────┘
3.1 Installation
────────────────────────────────────────────────────────────────────────
Installation is made simple. You must use the two configuration
programs to make patched versions of the original programs. You can
use the CFG-programs to alter the current version without having to
install options again and you can use the main programs to type-out a
new configuration which can be imported into newer versions.
First time installation is as follows:
- Put RFC.EXE somewhere on your hard-disk;
- Put RFCCFG.EXE in the same directory;
- Change to this directory and run RFCCFG (see below);
- Put RFW.EXE somewhere on your hard-disk;
- Put the RFWHLP.??? files somewhere on you harddisk, on the DOS-path
or along with RFW.EXE in the same directory (access depends on the
installation of RFW0;
- Put RFWCFG.EXE in the same directory;
- Change to this directory and run RFWCFG (see below);
- Add RFC.EXE somewhere in your batch file that runs your BBS (an
event) and/or behind the program that you use to alter the FILES.BBS
files;
│- Before you start running RFC in your even, you should at least run
│ RFC once with the /ALL option added on the command-line;
- For fastest access you can put the compiled files somewhere on a
RAM-disk, but make sure you created these files first on a fixed
disk;
- Put RFW.EXE in a type 7 at locations where you want to replace your
current files-list with this program (so at files-list, new-files,
keyword-search and file-search) as described be- low;
Upleveling to THIS release (1.20) goes as follows:
- Swap to the directory that contains the old RFW.EXE and RFC.EXE;
- Run the OLD RFW.EXE with the /CFG command-line option;
- Do the same with RFC.EXE;
- Replace the RFC.EXE, RFCCFG.EXE, RFW.EXE and RFWCFG.EXE with
the newer versions;
- Run RFCCFG.EXE and import the old configuration-file, then alter
the fields where needed;
- Run RFWCFG.EXE and import the old configuration-file, then alter
the fields where needed;
│- Run RFC.EXE with the /ALL switch once, because the format of the
│ database has been changed between 1.16 and 1.20 !
RFC.EXE makes two files (a compiled file-list and area-list). RFC can
(optionally) create temporary files first and when ready, RFC will
move these files over the old version. In this case you can run RFC
almost any time, even when the BBS if active and users use the
file-list.
RFC will take the area-file and compiles a list with records to be
displayed later. All extra info (like security level, area name, flags
and so on) is imported into the compiled list. Also CD-ROM (alternate
│files area's) are supported in RA 1.xx, RA 0.xx and SBBS 1.16+ mode.
│RFW has explicit support for the new RA 1.20 format. This release of RA
│is still in beta-test and the support for this version *can* well be
│incorrect when another change in the RA-structs is implemented.
When installing for the first time, you must run RFC from the command
line first to get a database. Later, in the event, a new list will be
created from inside the batch-file or after you have altered the files
│in FILES.BBS. When you run RFC for the first time, use the /ALL command
│line option !
RFW takes the compiled lists and creates a sub-list (depending on the
task-number) in memory, EMS, XMS or disk, depending on the resources
and the length of the list. The creation of a sub-list is needed
because only at execution-time of RFW, RFW knows the security level
and flags (and chosen option for that matter) and creates the sub-list
with this information. BUT only the compiled list is accessed on a
very fast speed and not all individual files. It should be clear that
RFW.EXE points to the same compiled files that RFC.EXE has created.
Also ensure that the files are compiled, at least, every day otherwise
your users won't see new files for a long, long time.
3.2 Install RFC
────────────────────────────────────────────────────────────────────────
Both RFC and RFW have to be installed first, because it is almost sure
that you can not use the supplied defaults (except the colors).
Better, when RFC and RFW are not installed at least once, they will
abort !
When you start RFCCFG.EXE, you will get the following questions:
╒══════════════════════════════════════════════════════════════════════════════╕
│ You can now select the type of BBS you run RFC on. Currently there │
│ are four types supported, QuickBBS <tm>, Remote Access 0.xx /1.xx │
│ and SBBS. │
│ NOTE : Use <ESC> to abort installation and read documentation !! │
│ │
│ You can enter the following types: 1 - QuickBBS <tm> Rel 2.74- │
│ 2 - Remote Access <tm> Rel 0.xx │
│ 3 - Remote Access <tm> Rel 1.0x │
│ 4 - SBBS <tm> Rel 1.16+ │
│ 5 - QuickBBS <tm> Rel 2.75+ │
│ 6 - Remote Access <tm> Rel 1.1x+ │
││ 7 - Remote Access <tm> Rel 1.2x+ │
││ 8 - Maximus <tm> Rel 2.xx │
│ │
│ Type of BBS RFC will assume : 6 │
╘══════════════════════════════════════════════════════════════════════════════╛
RFC needs to know the type of BBS you are running. This information is
needed to read the proper area-file and it's layout. For the Remote
Access flavors, point to the FILES.RA file. For the old QuickBBS type
you should point to FLSEARCH.CTL and the new QuickBBS type should
point to the FILEAREA.DAT file. The SuperBBS type should point to its
│own file (FLSEARCH.BBS, not CTL). The MAXIMUS <tm> support is not yet
│implemented in RFC, so this option can not be selected. When you run
│the RA 1.20 beta release (A or B), you should try to use RA 1.2x on
│RFC but try RFW with both 1.1x or 1.2x versions. RFC needs the new
│FILES.RA structure but your RA-beta could well use the OLD 1.1x format
│for EXITINFO.BBS (this is why you need to install RFW with 1.1x). Newer
│RA-beta versions *could* use the new EXITINFO.BBS format and RFW should
│be installed with explicit 1.20 support.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for area-file to use : D:\BBS\RAX\FILES.RA │
╘══════════════════════════════════════════════════════════════════════════════╛
This field must point to (one of your) area-files. RFC will take this
file to create the compiled list. See the description above to see
which file is needed for what type of BBS.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path to alternate FILES.x files (CD-ROM) : D:\BBS\RAX\FIL\ │
╘══════════════════════════════════════════════════════════════════════════════╛
This question will only be asked when you use a RA 1.xx (and higher)
type of BBS (not for RA 0.xx). This directory must point to the same
directory you have installed with RACONFIG and that points to the
directory where alternate FILES.n (where n is the file-area number)
are stored;
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for compiled file (CMP): D:\BBS\RAX\RFC.CMP │
╘══════════════════════════════════════════════════════════════════════════════╛
This field must contain the name of the compiled files-list. This
field must point to the same file as supplied in RFW.EXE. You must
supply the full drive, path and name otherwise RFCCFG.EXE will
complain.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for compiled area-file (ARE): D:\BBS\RAX\RFC.ARE │
╘══════════════════════════════════════════════════════════════════════════════╛
This field must contain the name of the compiled area-list. This field
must point to the same file as supplied in RFW.EXE. You must supply
the full drive, path and name otherwise RFCCFG.EXE will complain.
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Directory for temporary files : G:\ZIP │
│╘══════════════════════════════════════════════════════════════════════════════╛
│This field must point to a drive and directory that will contain the
│temporary files that RFC can create. In this directory, RFC will store
│the CD-ROM area's overhere (see chapter on CD-ROM) when a new file is
│compiled ! Depending upon the number of CD-ROM area's you have, the
│drive must have from 0 to the size of the current compiled file bytes
│free.
│
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Drive, dir and name of the FILES.CTL or empty : D:\BBS\RAX\FILES.CTL │
│╘══════════════════════════════════════════════════════════════════════════════╛
│This field must point to a drive, directory and name of the FILES.CTL
│file (if you have any). If there isn't such a file available, you can
│leave the field empty. When the FILES.CTL will always be in the current
│directory at the moment RFC starts, you can leave out the directory and
│the drive. Both RA, QBBS and SBBS formats of the FILES.CTL are allowed.
│RFC will use the information from this file to detect which files are
│free-files and which contain a password. RFW can display this info when
│it displays a file-list.
│
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Enable keyword search INSIDE files [Y/N] : Y │
│╘══════════════════════════════════════════════════════════════════════════════╛
│RFW can search for keywords inside non-archived files (like text files
│on your BBS). When you allow this option (see RFWCFG.EXE), you must
│also instruct RFC to do something extra. When you allow this option in
│RFCCFG.EXE (so RFC will do "its's thing") you can also set the option
│in RFWCFG.EXE. When you don't set the option in RFCCFG, you can still
│set the option in RFWCFG but RFW will NEVER look inside non-archived
│files.
│
│This option is configurable because RFC will mark those files that are
│non-archive files. To do so, RFC will have to open each file while it
│compiles the database. This will cost extra time and will be of little
│use when you don't have much text-files and/or you won't allow your
│users to search inside these text-files.
│
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Starting character of FILES-counter [empty=none] : [ │
││ Ending character of FILES-counter [empty=none] : ] │
│╘══════════════════════════════════════════════════════════════════════════════╛
│Normally your FILES.BBS files will contain files-counters and these
│will start with the '[' character and end with the ']' character, like
│[001] or [1]. If you don't use any files-counter, you can leave these
│fields empty. When you use OTHER characters (like '{' and '}') you
│must supply them overhere. RFC will use this information so it can
│adjust your comments AFTER the counter (nicer look).
╒══════════════════════════════════════════════════════════════════════════════╕
│ Use original files only a short moment [Y/N] : Y │
╘══════════════════════════════════════════════════════════════════════════════╛
If you supply a 'Y', RFC will compile $$$RC$$$.CMP and $$$RC$$$.ARE in
the current directory first and after compilation is ready, it will
delete the original files and move these files to the right place and
with the right name. Make sure you have enough space on your hard-disk
because you need the full amount of space the compiled files
use,twice.
3.3 Install RFW
────────────────────────────────────────────────────────────────────────
When you start RFWCFG.EXE, you will get the following questions:
╒══════════════════════════════════════════════════════════════════════════════╕
│ You can now select the type of BBS you run RFW on. Currently there │
│ are four types supported, QuickBBS <tm>, Remote Access 0.xx /1.xx │
│ and SBBS. │
│ NOTE : Use <ESC> to abort installation and read documentation !! │
│ │
│ You can enter the following types: 1 - QuickBBS <tm> Rel 2.74- │
│ 2 - Remote Access <tm> Rel 0.xx │
│ 3 - Remote Access <tm> Rel 1.0x │
│ 4 - SBBS <tm> Rel 1.16+ │
│ 5 - QuickBBS <tm> Rel 2.75+ │
│ 6 - Remote Access <tm> Rel 1.1x+ │
││ 7 - Remote Access <tm> Rel 1.2x+ │
││ 6 - Maximus <tm> Rel 2.xx │
│ │
│ Type of BBS RFW will assume : 6 │
╘══════════════════════════════════════════════════════════════════════════════╛
The same question as with RFCCFG.EXE. Look into the previous chapter !
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for compiled file (CMP): D:\BBS\RAX\RFC.CMP │
╘══════════════════════════════════════════════════════════════════════════════╛
Must be the same name as you supplied in RFCCFG.EXE.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for compiled area-file (ARE): D:\BBS\RAX\RFC.ARE │
╘══════════════════════════════════════════════════════════════════════════════╛
Must be the same name as you supplied in RFCCFG.EXE.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for ANS help-file or EMPTY : │
╘══════════════════════════════════════════════════════════════════════════════╛
You must use your own HELP-files. This option must point to the name
location of the help-file for ANSI-users. If you leave this option
empty, RFW will search for RFWHLP.ANS (or RFWHLP.ASC) in one of the
following locations:
- Current directory;
- Directory where RFW.EXE is stored;
- Dos-path;
If an ANS-file is not present, RFW will try to search for an ASC-file.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Drive, path and name for ASC help-file or EMPTY : │
╘══════════════════════════════════════════════════════════════════════════════╛
See previous question.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Location of tag-file, *CUR-current dir or EMPTY : D:\BBS\RAX │
╘══════════════════════════════════════════════════════════════════════════════╛
With the release of FileDoor <tm> a new type of file is introduced to
support the tag-function of FileDoor. This FileDoor/DISP-compatible
file must be created in a certain directory. This must be the same as
your FileDoor.CFG configuration points to. Various BBS's handle this
file in a different way. SuperBBS, which can create FileDoor/DISP
tag-files, will place the tag-file in the current directory on each
and every line you run. Remote Access can use one common directory for
all line. You can supply:
- A VALID directory. RFW will always put the BBSTAGFL.x files inside
this directory (RA flavor);
- You can supply *CUR in which case RFW use the CURRENT directory to
│ put the tag-file in (use this with SBBS);
- You can leave the field empty. In this case RFW wil not use tagging;
╒══════════════════════════════════════════════════════════════════════════════╕
│ Do you want scrolling and no clear-screen [Y/N] : N │
╘══════════════════════════════════════════════════════════════════════════════╛
You can choose from either two options:
- The screen is will clear before the next screen is drawn. This is
the fastest option and most SysOp's will use it I imagine. In this
case you supply a 'N';
- The screen is redrawn OVER the current screen. This is the same as a
normal DOS application but because of the low speed (2400 and less)
this can look a bit messy. In this case you use a 'Y';
'Y' tends to be somewhat slower but the result of 'N' is more
appealing for the eye when running high-speed modems;
╒══════════════════════════════════════════════════════════════════════════════╕
│ Do you want a top-ruler (start of list) [Y/N] : Y │
╘══════════════════════════════════════════════════════════════════════════════╛
You can choose to display 'TOP OF LIST' as a ruler. If you don't want
this, you must supply 'N';
╒══════════════════════════════════════════════════════════════════════════════╕
│ Do you want a bottom-ruler (end of list) [Y/N] : Y │
╘══════════════════════════════════════════════════════════════════════════════╛
You can choose to display 'BOTTOM OF LIST' as a ruler. If you don't
want this, you must supply 'N';
╒══════════════════════════════════════════════════════════════════════════════╕
│ Highlight the uploaders name (XFD format) [Y/N] : Y │
╘══════════════════════════════════════════════════════════════════════════════╛
RFW can, optionally, display the name of the uploader in a different
color. RFW expects comments that are fully compatible with those that
are created by FileDoor <tm> 'uploadername' option. In this case it is
also needed that the uploaders name is in the +-comment-line flavor !
If this options results in bad screens or colors, you can set this
option to 'N', otherwise use 'Y'.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Only use specified /A for search and new [Y/N] : N │
╘══════════════════════════════════════════════════════════════════════════════╛
Normally you only have to supply /A when you use RFW as a multiple
choice list ('do you want to list, search, list new files') or when
you only want to list files.
If you want the /A also to work WITHIN new-files and the search, you
must supply a 'Y'. In this case a search will only be conducted in the
area you supplied with /A. The same goes for new-files. By default you
should use 'N' in this option unless you know what you are doing.
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Enable keyword search INSIDE files [Y/N] : Y │
│╘══════════════════════════════════════════════════════════════════════════════╛
│When you have set the same option in RFCCFG to 'Y', you can also set
│this option to 'Y' overhere. When enabled in both RFCCFG and RFWCFG,
│the user can do a keyword search that will also look inside any non
│archived files (like text files). The search algorithm for these type
│of searches is very fast and will not reduce the overall speed of RFC
│very much, but all depends on the actual number of non-archived files
│you have and their combined size.
│
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Text when in-file keyword matched : [KEYWORD INSIDE] │
│╘══════════════════════════════════════════════════════════════════════════════╛
│This option can be used to change the default text that RFW displays
│when an 'inside match' is found.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Date format to use (use d/D/m/M/y/Y and sep.char): mm/dd/yy │
╘══════════════════════════════════════════════════════════════════════════════╛
You can supply the date-format in the files-list. Any combination
(within 8 characters and using the supplied characters) is valid
(yy/mm/dd, mm-dd-yy, yy:dd:mm and so on). Be sure to include 8
characters, otherwise the file-list can be somewhat shifted at several
places (only when you use multiple line comments). A capital
character means 'suppress leading zero' a lower-case character means
'display leading zero'.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Priority of memory usage [C/E/X/V/blank] (DOC) ): CEXV │
╘══════════════════════════════════════════════════════════════════════════════╛
This is a tricky one. RFW uses a special array of information that can
(must) be stored virtual. It extends the normal 64K bounds in a way
that is similar as with Windows 3.x <tm>. RFW will need to know in
which priority you would like to store the information. What RFW will
do, is to look in the priority list you supply over here. If there is
room enough in the first type of memory, it is used, otherwise the
second is tried, or the third or the fourth. You MUST at least specify
ONE type. Under normal situations, the default (CEXV) will do unless
you want to swap priorities (f.i. XMS before EMS, thus CXEV) or you
have problems with RFW and some type of memory.
Possible values are:
C : Conventional memory. With very large databases, this type will
almost never be used. If this is the case, you can leave this
type out, though the test will not take much time and IF the
array fits, you get a large gain in speed;
E : EMS memory.
X : XMS memory.
V : Virtual memory (disk!). ALWAYS include at least this type !
blank : Nothing
For example, you want priorities XMS, EMS and Virtual. You should set
the value to XEV. The fourth entry is empty and will not be used. When
EMS, Conventional, Virtual, XMS should be the priority, you supply
ECVX.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Clear arrays (will cost extra time) [Y/N] : N │
╘══════════════════════════════════════════════════════════════════════════════╛
This is more or less a debug option. This option should ONLY BE SET to
YES is you sometimes have problems with your hard-disk (disk errors) or
you experience problems with RFW (trashed screens, strange files). If
set to Y, RFW will first initialize the virtual (tmporary) array and
will then set all array-entries to a value. Normally this is not needed
because RFW knows which array-entries are used. When set to N, RFW
will still initialize the array but will NOT set all array-entries to a
value. With large compiled files (+500.000 files), this will reduce the
waiting (on the user's side) considerable ! Leave it to N under normal
conditions.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Location virtual array file (empty = current dir): │
╘══════════════════════════════════════════════════════════════════════════════╛
If the compiled file gets very large and there are not enough resources
available (EMS, XMS or conventional memory) to store all records, RFW
will create a virtual array on DISK. Normally (if you leave the field
empty, and for all older versions of RFW), the array would be written
to the current directory. If this drive is rather small or you want to
use a faster drive (ram-disk), you can use this option to point to the
directory where the file should be stored (each RFW on each different
line will use a unique file-name). Remember that the drive must contain
around 1 1/2 times the space of the RFC.CMP file (compiled file) for
EACH line you run (in case ALL lines use RFW at the same time). In
those cases where the SysOp uses a very large RAM-disk, this disk can
be used, it it is big enough.
│╒══════════════════════════════════════════════════════════════════════════════╕
││ Calling sequence for viewer (empty = no view) : C:\SYS\OWN\MTS.EXE /F$F / │
│╘══════════════════════════════════════════════════════════════════════════════╛
│RFW can view files that are listed. Like 'T' (tagging) you can enter a
│'V' to view inside one or more files after each other. Because most
│files will be archives, you have to use an archive viewer that can also
│display non-archived files, like the DISP <tm> program MTS <tm>. When
│you install a view-program, you must supply the calling sequence for
│this program. In the calling parameters you can add one or more macros
│that will be expanded by RFW at run-time. These are:
│
│$C : Will be replaced by the actual COM-port
│$B : Will be replaced by the baud-rate
│$T : Will be replaced by the remaining time left for this call;
│$L : Will be replaced by the BBS line number
│$F : Will be replaced by the name of the file that must be viewed
│$M : If set, RFW will swap out of memory before the call to the view
│ program is made (recommended!);
│
│In the installation version that you obtained from the release archive
│you can already find an example to call DISP <tm> program MTS <tm>.
╒══════════════════════════════════════════════════════════════════════════════╕
│ Color for headers ( low) : <TEST> Blink: N │
│ Color for headers (high) : <TEST> Blink: N │
│ Color for header-1 : <TEST> Blink: N │
│ Color for header-2 : <TEST> Blink: N │
│ Color for header-3 : <TEST> Blink: N │
│ Color for header-4 : <TEST> Blink: N │
│ Color for header-5 : <TEST> Blink: N │
││ Color for statusline (low) : <TEST> Blink: N │
││ Color for statusline (high) : <TEST> Blink: N │
│ Color for top-ruler : <TEST> Blink: N │
│ Color for bottom-ruler : <TEST> Blink: N │
│ Color for art-work/comments : <TEST> Blink: N │
│ Color for filename : <TEST> Blink: N │
││ Color for pwd.prot. marker : <TEST> Blink: N │
│ Color for filesize : <TEST> Blink: N │
││ Color for freefile marker : <TEST> Blink: N │
│ Color for filedate : <TEST> Blink: N │
│ Color for file-comment : <TEST> Blink: N │
││ Color for in-file ks-match : <TEST> Blink: N │
│ Color for XFD uploader name : <TEST> Blink: N │
│ Color for new files : <TEST> Blink: M │
│ Color for error messages : <TEST> Blink: N │
│ Color for area-separators : <TEST> Blink: N │
│ Color for help-line ( low) : <TEST> Blink: N │
│ Color for help-line (high) : <TEST> Blink: N │
│ Color for tag-option letter : <TEST> Blink: N │
│ Color for tagged file char : <TEST> Blink: Y │
╘══════════════════════════════════════════════════════════════════════════════╛
You can alter ANY (except the local information window) color in the
list. For every option you can select one of 128 different color
combinations. Use N to see the next, P to see the previous and T to go
to the first (black) color in the list. Use ENTER to select the color
and then use 'Y' or 'N' to select if you want this field to blink !
│The two 'marker' options can result in a complete circus show (for your
│taste). If so, you can use 'black' as the color and they won't be shown
│to the user (they are shown, but black letters on a black background
│are hard to see).
It is NOT possible (yet) to configure RFW in a way that the COMPLETE
background is reversed. This is also somewhat slower for the user and
thus (also) not a good idea.
3.4 BBS menu options
────────────────────────────────────────────────────────────────────────
RFW needs to be installed in a type 7 (or 15) in the BBS menu(s). RFW
needs some command-line options to do its work. These are:
╒══════════════════════════════════════════════════════════════════════════════╕
│ /A[area to display] │
╘══════════════════════════════════════════════════════════════════════════════╛
/A is only needed with /LF but can always be supplied (if this makes
it more transparent to you). Only when you select a special option in
RFWCFG.EXE, /A has a meaning with all other options than /LF (see
above). You must include the same path as you have supplied in the
FILES.RA file. So if all your paths are without a drive-letter, you
must also leave the drive-letter out over here. It is better to use
the standard RA <tm> option *0 because this is the same path/area as
in FILES.RA. So by default, use /A*0 in your type 7 or 15 menu record.
(*0 works only with RA 0.03 and up !).
╒══════════════════════════════════════════════════════════════════════════════╕
│ /N[line] │
╘══════════════════════════════════════════════════════════════════════════════╛
This option is important when you run a multi-line BBS. Include /N*N
in your type 7 or 15 if this is the case. If you forget this option,
two concurrent RFW programs, could use the same EMS/Disk-space when
they are running, causing a mess on the screen and a hangup of your
machine.
╒══════════════════════════════════════════════════════════════════════════════╕
│ /LF (*) see below │
╘══════════════════════════════════════════════════════════════════════════════╛
When you supply this option, RFW will get into 'list files' mode and
needs a /A to perform its task. Only files in the supplied area are
listed.
╒══════════════════════════════════════════════════════════════════════════════╕
│ /NF (*) see below │
╘══════════════════════════════════════════════════════════════════════════════╛
When you supply this option, RFW will get into 'list new files' mode.
You don't have to supply /A, unless in special cases (see RFWCFG.EXE).
│╒══════════════════════════════════════════════════════════════════════════════╕
││ /NFEMSI (*) see below │
│╘══════════════════════════════════════════════════════════════════════════════╛
│This is the same as /NF but now RFW will not ask for confirmation of
│the last scan-date. This option can be uses to replace the RA/SBBS
│internal EMSI new-file scan. You should need a program like I2FLG100.*
│(created by Hans Siemons) to set and test the correct switches and
│flags. With the help of this program (examples for RA_NEW are included
│but can be replaced by RFW) and this switch the internal EMSI new-file
│scan can be replaced.
│You don't have to supply /A, unless in special cases (see RFWCFG.EXE).
╒══════════════════════════════════════════════════════════════════════════════╕
│ /KS (*) see below │
╘══════════════════════════════════════════════════════════════════════════════╛
When you supply this option, RFW will get into 'search for keyword'
mode. /A is not needed unless in special cases (see RFWCFG.EXE).
╒══════════════════════════════════════════════════════════════════════════════╕
│ /FS (*) see below │
╘══════════════════════════════════════════════════════════════════════════════╛
When you supply this option, RFW will get into 'search for files'
mode. /A is not needed unless in special cases (see RFWCFG.EXE).
╒══════════════════════════════════════════════════════════════════════════════╕
│ /KF (*) see below │
╘══════════════════════════════════════════════════════════════════════════════╛
When you supply this option, RFW will ask a question to the user if
she/he want to go into search-keyword or search-files mode. /A is not
needed unless in special cases (see RFWCFG.EXE).
╒══════════════════════════════════════════════════════════════════════════════╕
│ /ASC │
╘══════════════════════════════════════════════════════════════════════════════╛
You will force RFW to use ASCII displays when you insert this option !
╒══════════════════════════════════════════════════════════════════════════════╕
│ /CFG │
╘══════════════════════════════════════════════════════════════════════════════╛
When /CFG is used on either RFC or RFW, the program will write a
configuration-file. This file can be used by RFWCFG and RFCCFG to add
the old information to any new release. RFC or RFW will stop after the
.CFG file is written;
╒══════════════════════════════════════════════════════════════════════════════╕
│ (*) now for something special │
╘══════════════════════════════════════════════════════════════════════════════╛
If you supply neither /LF, /NF, /KF, /KS or /FS, RFW will ask the user
what to do. The user can now select from any of the option and RFW
will perform this task. Because the user (at any time in the list) can
force RFW to go back to the start (to ask a new mask or date for
new-files), this is a powerful option. You only need one menu-item to
do all file (list) access in one strike.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 4 │ Runtime information │
└───────┴─────────────────────────────────────────────────────────────┘
4.1 Usage of RFW
────────────────────────────────────────────────────────────────────────
When RFW presents its list of files (if any), after the questions that
RFW (optionally) asks to the user, the user can do several things.
FIRST (and most important) is that the user must set his/hers NUM-LOCK
to on (also when running locally). If she/he forgets this, nothing
will happen unless 'Q', '?','N','T', [ENTER] or [ESC] is used.
Next the user can use '7' (simulate of HOME) to go to the top of the
list. '1' (simulate of END) to go to the bottom of the list. These two
options can also be used to redraw the screen.
'8' and '2' (simulate CRSR-UP and CRSR-DOWN) can be used to scroll one
line up or down at the time.
'9' and '3' (simulate PGUP and PGDN) can be used to scroll one page at
up or down at the time.
[ENTER] can also be used as a replacement of '3' (PGDN).
│RFW (from version 1.20 and up) will also support special key-protocols
│that the remote terminal package can send. These are the protocols that
│are known as the Maximus, TopEd and QuickEd protocols. When the remote
│package will emulate the cursor keys in one of these modes, RFW will
│correctly interprete them.
[ESC] will terminate the execution.
'?' or 'H' will force QFW to display its own help information or the
file you supplied with RWFCFG.EXE.
'N' can be used to reset RFW without leaving the program. In all modes
except /LF, this option can be used to let the user enter a new
selection (new search-mask or new date for new-files). If RFW runs
without /LF, /NF, /KS, /FS and /KF, 'N' will force RFW to go back to
the first question to ask the user the mode to run in.
'T' can be used to tag or un-tag files. When RFW starts, it will test
for the presence of a FileDoor/DISP-compatible tag-file. If this file
belongs to the user and was previously edited by RFW, the information
will be displayed to the user and the user can reuse (add/delete files
to the list) or delete the tag-file.
│'V' can be used to view files. When RFW starts, it will test if you did
│install an external viewer that can use the macros that RFW supports
│(see RFWCFG). When this is the case, the user is able to view files in
│the same way as she/he can tag files. A compatible viewer that can be
│used with RFW is DISP MTS <tm> program.
If RFW was not the last program that edited the tag-file, the user can
choose to terminate RFW or to delete the file.
If tagging is not set (e.g. RFW does not point to a directory that
will contain the tag-file), the user is left in peace and no questions
are asked.
With tagging, the user can tag/un-tag files from the list. Tagged
files will be stored in a list that can be used by FileDoor <tm> or
other 3th party vendor programs.
At the local side, you can also enter any of the above keys AND you
can enter CTRL-T to toggle RFW's information window. If this window is
set to ON, RFW will re-display this window (only at the local side)
with every change of the screen. If you toggle this option OFF again,
you must wait until the user changes the screen before the window is
gone again.
The user is able to enter any key while the screen is build. This
hot-key support looks much like the build-in hot-key support of RA.
RFW monitors the remaining time the user is allowed in the BBS, the
carrier (if carrier is lost, RFW will terminate and the BBS will take
over again) and if the user is not entering any key within 2 minutes.
If you want to have current user information, you must hit the CTRL-T
button. This button toggles the status-display !
4.2 FileDoor/DISP-compatible tag-file <tm>
────────────────────────────────────────────────────────────────────────
With release 1.10, RFW contains a full FileDoor/DISP-compatible
tag-file <tm> implementation. What does this mean.
The user is able to tag (or un-tag for that matter) files that
she/he would like to select from the list that RFW presents. Tagging
can be done with the <T>-key. A file already tagged can be
un-tagged, a file that is not tagged can be tagged (so <T> works like
a toggle).
When the user terminates RFW, RFW will write a special kind of file.
This file is called the FileDoor/DISP-compatible tag-file. This file
has a uniform format and can be read by most door-like DISP programs
and (its primary reason of being there) by FileDoor <tm>. When the
FileDoor <tm> program detects such a tag-file, it will test if the
file belongs to the current user (if not, it will be deleted) and the
file will (or can) be used as input for the file-selection inside
FileDoor (download/Bidirectional). RFW creates a so called auto-tag
file. This means that FileDoor will start reading the tag-file without
asking the user. The user is still able though, to select or reject
the presented choice.
When RFW has created a tag-file and the user enters RFW again (while
there is still a tag-file from the same user), the user has the option
to reuse the tag-file or to delete it. If the file is reused, RFW will
show all files already tagged before and will keep files from other
areas inside the tag-file. The user can now change the tagging (set it
to off) or add new files. Before termination, RFW will merge the new
results in the old tag-file. In this way, the user can scroll thru
various areas and can create a combined tag- file that can be used
with FileDoor (if autosearch is set to on). Deleting the tag-file
means that the old tag-file is flushed and (optionally) a new one is
created.
When FileDoor <tm> has used the RFW tag-file, the auto-tag switch is
set to off. If the user enters FileDoor again, the tag-file must be
selected by hand (/TAG).
A description of the FileDoor/DISP-compatible tag-file is included in
the supporting programs at the moment that the internal structure is
released for public usage. In this case a file called FDTAGSTR.xxx
(where xxx is the version of the used format, currently 201) is added
to the archive.
Programs that will support this kind of tag-file are, MTS, RFW and
FileDoor itself. Other products can choose to use the functions of
such a tag-file.
4.3 CD-ROM matters
────────────────────────────────────────────────────────────────────────
RFC will compile from the BBS-area file and the FILES.BBS files but
still needs the actual files because the file-sizes and dates must be
obtained somehow. On a CD-ROM drive (with tons of files) this can
result in very long waiting times in RFC. RFC 1.20 fixes this problem.
The new compiler (RFC.EXE) works as follows:
- The first time (when there isn't a previous compiled file or when
you run RFC with /ALL), RFC will actually compile ALL areas, also
including the CD-ROM areas;
- The next time RFC is executed (without /ALL), RFC will first search
thru the old database to find the areas that came from a CD-ROM
device. These areas are seperated from the old compiled file and
put into the temporary directory (not the files but the records
from the database, just to make sure);
- RFC deletes the old database and starts collecting the information
from the area-file and the FILES.BBS files. At the moment it hits
a CD-ROM area, it will look to see if there were pervious records
from this area. If there were, these records are merged into the
new database WITHOUT accessing the CD-ROM at all. If there weren't,
RFC will access the CD-ROM and will add the area to the new database;
- While merging records, RFC will update the name of the area and the
actual security levels and flags, so when you just altered the name
of the area (not the location) and/or the security level, RFC will
still not access the CD-ROM EVEN when you changed the position of
the area in the area-file (f.i. from slot 100 to slot 80);
- RFC will merge the records based on the location inside the area-file
so they will always be in the correct order;
How does RFC deside if an area is a CD-ROM area ? Simple. For RA it
will be a CD-ROM area when there is a FILES.x in the alternate files
path (see RFCCFG and RACONFIG), for SBBS, it will simply get the info
from the FLSEARCH.BBS. All area's that have different directories for
the files and the FILES.BBS are marked as CD-ROM areas !
If you changed many things in the CD-ROM areas and/or you are not sure
about the information inside the RFC-database, you can use a special
command-line option for RFC, the /ALL command-line parameter. When you
supply /ALL, RFC will recompile all areas without merging old info from
previous compiled databases and will obtain all info from the CD-ROM.
This information is given to supply you with the most complete info
about RFC's CD-ROM handling and can also be used by some other people
who are known to copy the best of all other programs to produce a
clone of their own (it is a hard world, but it is)....
┌───────┬─────────────────────────────────────────────────────────────┐
│ 5 │ Version information and credits │
└───────┴─────────────────────────────────────────────────────────────┘
5.1 The BETA-team
───────────────────────────────────────────────────────────────────────
Look into the file SUPPORT.MTA for a full list of all beta-testers and
support nodes.
5.2 Credits
───────────────────────────────────────────────────────────────────────
Thanks to the following people (besides my eternal thanks for the
BETA team):
- All paying, registered users. You made it possible to enhance
MTA with nice features;
- All users who did write me bug reports, suggestions and so on;
- Ati Antman and Risto Virkkala for their support for DISP products
and their fine BBS.
5.3 Version history
────────────────────────────────────────────────────────────────────────
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.01 │ Beta release │
└───────┴─────────────────────────────────────────────────────────────┘
■ First non-public beta release;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.02 │ Beta release │
└───────┴─────────────────────────────────────────────────────────────┘
■ First public beta release;
■ Changed the RFC.CMP into two files (RFC.CMP and RFC.ARE) to gain
memory;
■ Changed access to RFC.CMP, thus creating a gain in speed. A
benchmark with 5000 files in FILES.BBS under DesqView gave the
following results:
1.01ß2 Stored in memory : 87.56 seconds
1.02ß4 Stored on DISK ! : 30.80 seconds
A benchmark with 2000 files in FILES.BBS under DesqView gave the
following results:
1.01ß2 Stored in memory : 37.67 seconds
1.02ß4 Stored in memory : 9.61 seconds
■ Fixed some extended ASCII traps, so ASCII (non ANSI) users can now
look at a clean screen;
■ Fixed name of program in program header (QFW was displayed and not
RFW).
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.03 │ First public release │
└───────┴─────────────────────────────────────────────────────────────┘
■ Added Hot-key support
■ RFW is now capable of displaying more than 24 lines if the user did
set a larger number of lines in the user-setup of the BBS;
■ It is now configurable to choose between clear-screen/display and
scrollwindow/display;
■ It is now possible to let the 'TOF'/'BOF' rulers out of the list;
■ It is now possible to configure all colors (local and remote);
■ It is now possible to configure the format the date that RFW
displays in the files-list;
■ You can replace the internal help-screen with your own files. While
displaying this file, Hot-key support is NOT active;
■ It is now possible (with a special configuration option, to keep
downward compatibility) to combine the /A option with all other
options to reduce the search/display to one area;
■ With keyword/file search any long comment (displayed on a next line
in a normal file-list) was not displayed and/or searched. This is
now fixed (in a somewhat cruel way).
■ The user can now force RFW to restart without loading itself again.
■ Fixed some bugs and flaws;
■ Fixed time-slice problems in DV. In combination with X00 (DV
option) there is no degradation in performance, even with 8 RFW's
concurrent in the machine;
■ Changed the internal structure of the compiled files again. This
gives you a gain of 3 bytes per line. You must run RFC again when
upgrading to this version !
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.04 │ Bug release │
└───────┴─────────────────────────────────────────────────────────────┘
■ Changed the hotkey-support somewhat. Overrun errors should be fixed
now. Also several hits on ENTER or PGDN would result in a partial
displayed screen. This is also fixed;
■ Fixed RFC to work OK on both the old structure of FILES.RA and the
one introduced with RA 1.00beta8.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.10 │ Minor release │
└───────┴─────────────────────────────────────────────────────────────┘
■ Changed the hot-key support. RFW was know to eat many ticks. This
was caused by the special routines that implemented the hot-keys.
All keys will now ALWAYS redraw the screen, so CRSR-DOWN when the
last line is on the screen will still cause a redraw of the screen.
The same goes for CRSR-UP, END, HOME, PGUP and PGDN. Hot-keys
should now work better and with a smaller number of cycles.
■ Added support for QuickBBS and SBBS;
■ Added support for CD-ROM drives in RFC;
■ Added /CFG to RFW and RFC and /ASC to RFW;
■ Added tag-file support to create and use FileDoor/DISP-compatible
tag-files;
■ Removed help information from RFW. This is now stored in a separate
help-file (example included);
■ Changed the FOSSIL-access a bit and changed the input-routines to
give back more time-slices to DesqView <tm>;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.15 │ Minor and bug-fix release │
└───────┴─────────────────────────────────────────────────────────────┘
■ RFC is now configured for RA 1.1x, QBBS 2.75+ and SBBS 1.16+. This
makes a list of 6 different types of BBS's (and versions) that can
be supported. SBBS does not need the FLSEARCH.CTL anymore but will
directly support FLSEARCH.BBS. Structures for RA 1.11 and QBBS 2.75
and higher are included in RFC(CFG) and RFW(CFG);
■ CD-ROM should now work ok (RA 1.0x and RA 1.1x) again. Please
report if this is still a problem;
■ RFC would terminate when FILES.BBS was gone or corrupt. It will now
continue with the next area and give a warning;
■ RFC had some strange logic as to what was a file and what should be
a comment (artwork) in FILES.BBS. RFW will now mark a line as a
file when a valid DOS-filename character is entered ('*' and '?'
are excluded). If a line starts with a high-character or a space,
it is seen as artwork, unless a +-comment combination is present;
■ It is now impossible to tag files which was actually artwork. This
could cause bugs in FileDoor <tm> when a line with all '*' was
tagged;
■ RFC will now report errorlevel 255 when aborted due to an error;
■ RFW will not beep anymore when the large array is swapped to EMS,
XMS or disk;
■ RFW will not display the type of memory that is in use anymore;
■ RFW would sometimes screw the display (colors). This is now fixed;
■ RFW could leave EMS blocks when the carrier was lost before RFW
could terminate. Fixed;
■ RFW would display strange screens with keyword search. Now the
complete block (file + comments) is displayed correctly;
■ RFW could report error 204 when termination or hang with a #8/#127
combination. Both should be fixed;
■ RFW would flash the 'new-file marker' when a user selected new
files before the previous log-in. These files are not actually new,
so the new-file marker is now only displayed for actual new files
in the new-files list;
■ RFW would look at the download security field and not at the list
security (RA). This is fixed;
■ RFW would still allow tagging, even if tagging was switched off. The
menus could be trashed while still no tag-file was written. This is
fixed. If tagging is set to off, no tagging is possible inside the
screens;
■ RFW screens about reusing tag-files would report 'IGNORE' where
'DELETE' was meant. Fixed;
■ RFW would not allow empty entries while tagging. It is now possible
to 'undo' the tag-option by hitting ENTER;
■ RFW would allow empty entries with 'file-mask' and 'keyword'
but would select EVERYTHING. Now RFW will terminate when an empty
line is entered;
■ RFW would expand RFW as the file-mask to RFW.*. This is changed so
that RFW is expanded to RFW*.*. RFW_V115 is expanded to RFW_V115.*;
■ RFW would rebuild the screen when files were tagged. On great
demand this has been changed. In ANSI mode, RFW will now UPDATE the
correct lines and not redraw the entire screen;
■ RFW would allow configured colors for the tag-letter and the tag
marker. Though you could specify them in RFWCFG, RFW would always
force to YELLOW (letter) and LIGHTRED (mark). Fixed;
■ RFW will now allow configurable memory usage (see RFWCFG.EXE) to
store the virtual array of data;
■ RFW would always point to the same directory for the tag-file. In
SBBS environments this meant that you needed two RFW.EXE files. It
is now also possible to write (and search) the tag-file in the
current directory (*CUR in RFWCFG);
■ RFW can now display the name of the uploader in a different color
when you use the Filedoor <tm> +-comment-line type of uploader
information;
■ RFW can now make use of the DISP-compatible and 4DOS-compatible
wildcards (=RFW and *RFW*). This is (obvious) only possible with the
find-file option;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.16 │ Minor and bug-fix release │
└───────┴─────────────────────────────────────────────────────────────┘
■ RFW can now be configured to clear (or not clear) the virtual array
before usage. Under almost ALL conditions, use the value 'N' (not
clear the array) to gain speed;
■ RFW can now be configured to place the temporary (virtual) array in
a directory of your own likes. Normally, RFW would place the file
in the CURRENT directory, but now you can choose one of your own;
■ RFW has gained speed again. This is the main topic for this release.
Within a few days, some angry users called to tell that RFW was too
slow for their taste and skipped back to 1.10. I have replaced the
complete logic for this feature and will give some background. The
old 1.10 would read 40960 bytes at a time and would 'combine' these
bytes to records (a rather tedious routine, but fast). This resulted
in the problems with 'keyword search' only being able to display the
actual line where the keyword was found and not the complete file.
1.15 changed the routines. Now each and every record of 111 bytes
was read (binary) and the 'keyword search' looked much better. The
speed was ok on most single tasking machines but on networks, non
cached systems AND sometimes in combination with Desqview/SHARE,
the performance dropped to an abnormal depth. 1.16 has new routines
for reading. The compiled file is opened twice, once as a binary
(untyped) file and once as a binary typed file. Now for all routines
the untyped mode is used and chuncks of 590 records at a time (this
is almost 64K) are read. Only with keyword search, the typed file is
used to read back in the file (ONLY WHEN NEEDED, so ONLY WITH MULTI-
COMMENT files). This change is benchmarked, giving the following
results:
Compiled file : 64359 files, 7.143.849 bytes in size (HUGE!)
2 areas, area 1 contains 10 files and area 2
contains the remaining 64349 files:
RFW 1.15 List area 2 : 397.48 seconds
List area 1 : 193.82 seconds
RFW 1.16 (clear array) List area 2 : 290.34 seconds
List area 1 : 111.59 seconds
RFW 1.16 (NOT clear array) List area 2 : 142.26 seconds
List area 1 : 26.26 seconds
All on a 386/33 without cache and a 35 Ms hard-disk. As you can see,
the default 1.16 configuration (without clear of the array) is some
2.7 times faster when a list of 64349 files must be listed (this is
very exeptional, and still takes 2.5 minutes because of huge disk
writes). When you list a small area, the gain in time is some 7.4
times faster. In comparison with 1.10 (there were fewer tests in
1.10, so it is not a completely equal compare), 1.16 is still faster
with new-files, filename-search and list and somewhat slower when a
keyword search is performed.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1.20 │ Major release │
└───────┴─────────────────────────────────────────────────────────────┘
■ Fixed a problem in RFW where RFW would beep when the user dropped
the carrier. Caused many nights without good sleep, sorry;
■ Fixed a problem in RFWCFG. The alternate path setting would not
occur when RA 1.11 was the choosen type of BBS;
■ Fixed a problem in RFW. 'N' would not work or would only work one
time. Also memory trashing could occur;
■ Fixed a problem in RFW. '?' would trash the screen when used and
user had to redraw the screen again;
■ Fixed a problem in RFW. RFW kept one file open, causing some small
problems after running many times after each other;
■ Fixed a number of bad-spots in RFW which could all trash memory in
some sort of way. No reports of hangups until now (at least not
hangups that could be traced to RFW);
■ Keyword search would only display comments up to and including the
line that contained the match. This is fixed. All multi-comment
lines are now displayed;
■ Fixed ASCII mode again. Though many Sysop's are now talking about
swapping to a full-ANSI only BBS right now, I will still include
coding for those people who want to (or only can) run in ASCII
mode;
■ Fixed a problem with the time-check. RFW would allow unlimited
access (as long the user stayed in RFW). This is fixed;
■ Fixed a problem with SBBS CD-ROM entries. Previous versions would
not detect any CD-ROM file;
■ Fixed a problem with the screen routines for screen-clear mode. In
this mode the lines can be written until the last non-blank byte to
gain speed but RFW was still writing the full 79 characters;
■ Fixed a problem where RFC/RFW could not find the linking RFC.ARE
file if you changed the name of this file in either RFC or RFW;
■ Fixed a problem with RFCCFG. It is now allowed to leave the field
for the alternate FILES.BBS files empty;
■ Fixed a problem with RFW where RFW would create a tag-file that
would drive FileDoor <tm> wild;
■ Fixed a problem with RFW where [foobar] (not a counter) would cause
wrong adjustments in the display;
■ Fixed a problem with RFWCFG and RFCCFG. These programs will now
keep the original date/time and archive-bit when they patch RFW
and/or RFC;
■ New-files scan would allow dates in the future, this is fixed;
■ RFWCFG would only display the right color and not the name. To help
people with monochrome tubes or disabled people (those people who
can not see any colors), the name of the actual color is now
displayed;
■ Added options to allow both alternate date or number of days when a
new-file scan is entered and the user does not want to scan from
from the default date;
■ Added option to allow ESC while RFW is searching thru the database.
In this case RFW is aborted;
■ Added a statusbar at the bottom of the local screen so the sysop
can now always see who is using RFW and in what mode (the previous
versions included a ALT-T mode, which is now obsolete);
■ Added a progress-bar so the user can see that RFW is searching in
the database;
■ Added options in RFC and RFW to allow the user to scan for keywords
INSIDE non-archived files;
■ Added option in RFW to allow the <V>iew of one or more files. RFW
will call the specified viewing program. MTS <tm> will suit your
needs in this matter as it can view both archived files and non
archived files;
■ Changed the <N>ew option into <R>escan because it could confuse a
user. The user would think that this option would display the new
files. The old 'N' key is still allowed though;
■ Changed the location of the tag-marker. This marker (a '*') will
now be displayed behind the tag-letter and before the filename.
The previous versions would write the tag-marker behind the name of
the file. This change was needed to allow the 'P' (protected file)
to be displayed behind the filename;
■ Changed the recompile logic. CD-ROM areas have to be scanned only
once and will be merged into the database at the next compile
without having to access the CD-ROM itself. The SysOp can overrule
this logic by using /ALL on the RFC command-line;
■ Changed the memory logic for the virtual array that RFW uses. The
previous versions would assign a virtual array with a size equal to
the total number of records in all areas. The current version will
only use the actual number of records for a specific area. The
logic is only changed for the file-list function and not for the
keyword/file-search options and new-file scan. It can result in a
dramatical gain in speed and reduced memory consumption;
■ Added options to allow RFW to display markers when files are free
files and/or password protected files. You have to assign your
FILES.CTL in RFCCFG.EXE to let this option work;
■ Added the /NFEMSI option to RFW to allow RFW to replace any
internal EMSI new-file scan (with the help of a flag-test/flas-set
program like I2FLG100.* by Hans Siemons);
■ Added TopEd, QuickEd and Maximus cursor-key protocols to RFW. RFW
will interprete these cursor-empulations in the same way as you use
the numeric pad;
■ Added configurable counter starting/ending characters. Though these
are mainly for our Scandinavian friends, they could come in handy
when you don't use '[' and ']' as these characters;
■ Added some logic to support the upcomming RA 1.20 release;
■ Added logic for Commercial, Closed-BBS and beta-testing
registration keys;
■ Recompiled all programs under Borland Pascal 7.0 (real mode only,
on request a DPMI version can be created), which should result in a
gain in speed;
5.4 Copyright, Trademarks
────────────────────────────────────────────────────────────────────────
CRA is a trademark of DISP and donated to public domain
DesqView is a trademark of Quarterdeck inc.
Windows is a trademark of The Microsoft Corporation
4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson
FrontDoor is a trademark of J. Homrichhausen
QuickBBS is a trademark of Pegasus Software
SuperBBS is a trademark of the SuperBBS group, Aki Antman and
Risto Virkkala
Remote Access is a trademark of Continental Software
X00 is a trademark of Ray Gwinn
MTA is a trademark of Robert W. van Hoeven / DISP
MTS is a trademark of Robert W. van Hoeven / DISP
Filedoor is a trademark of Robert W. van Hoeven / DISP
RFW is written in Borland Pascal 7.0, with help of the Turbo Debugger
3.5 and makes extensive use of Object Professional 1.20. Also OPCFI
version 16.05 is included. Sub-development and special projects for
286/386-only environments is done with the marvelous StonyBrook
Pascal+ compiler version 6.14e.
Pascal+ is a trademark of Stony Brook Software
Borland Pascal is a trademark of Borland International
Turbo Debugger is a trademark of Borland International
Object Professional is a trademark of TurboPower Inc.
OPCFI and CFI is a trademark of Robert W. van Hoeven
========================= END OF DOCUMENT =============================